Band usage information generating and reporting method, charging method, enodeb, and mme

ABSTRACT

The present disclosure provides a band usage information generating and reporting method, a charging method, an eNB, a CN, a MME and a UE. The eNB and the UE can generate band usage information for charging, and report the band usage information to the CN, wherein the band usage information involves band usage of at least a first band and a second band, and traffic is assigned to respective bands by the eNB. The Counting entity at the eNB or UE can count the data volume of each band or ratio of data volume via different bands as the band usage information based on the scheduling information of the data. The Charging system located in the CN can process the charging and generate a bill according to the reported band usage information.

BACKGROUND 1. Technical Field

The present disclosure relates to the field of charging for wirelesscommunication, and in particular, to a band usage information generatingand reporting method, a charging method, an eNodeB (eNB), a core network(CN), a Mobility Management Entity (MME) and a user equipment (UE).

2. Description of the Related Art

Rapid growth of mobile data forces operators to utilize the finitefrequency spectrum with higher and higher efficiency, while plenty ofunlicensed frequency spectra are utilized less efficiently only by WiFi,Bluetooth, etc. LTE-U (LTE-unlicensed) could extend the LTE spectrum tounlicensed band that would augment the network capacity directly anddramatically. LTE-U with LAA (Licensed Assisted Access) has higherspectrum efficiency than WiFi especially when there are massive usersdue to for example reliable CCH (Control CHannel), LA (Link Adaption),HARQ (Hybrid Automatic Repeat Request), ICIC (Inter Cell InterferenceCoordination), interference cancellation. LTE-U could well co-exist withthe existed RATs (Radio Access Technologies) by following mechanism,e.g. LBT (Listen Before Talk), DFS (Dynamic Frequency Selection), TPC(Transmit Power Control). Network architecture will be more simple andunified.

In the scope of LTE-U, there are mainly two types of offloading asfollows.

1) CN (Core Network) offloading: different services via differentbearers, e.g. one bearer for WiFi (or LTE unlicensed frequency) andanother bearer for LTE licensed frequency. Currently, UE (UserEquipment) will automatically or manually switch to a WiFi network ifthe WiFi network is available no matter how crowded in unlicensed band.Similar to WiFi offloading, QoS (Quality of Service)/QoE (Quality ofExperience) via unlicensed band cannot be guaranteed due tocontention-based channel access, e.g. kinds of jitter.2) RAN (Radio Access Network) offloading: single bearer is split betweenLTE unlicensed frequency (or WiFi) and LTE licensed frequency at eNB(eNode B). The eNB would assign traffic to unlicensed and licensed bandsdepending on for example channel condition, traffic load and so on. QoScould be guaranteed by licensed band in case of unavailability of theunlicensed band, while QoE can even be improved when both licensed andunlicensed bands can be scheduled. FIG. 1 schematically illustrates RANoffloading of traffic, in which the traffic is assigned to a LTElicensed band and a LTE unlicensed band at the eNB.

Different from traditional CN offloading in which data is offloaded atCN based on user preference, RAN offloading in LAA can provide higherQoS/QoE and spectrum efficiency by utilizing cross carrier schedulingunder carrier aggregation architecture. Thus, RAN offloading can providemore advantage for promoting benefits of LTE-U.

Similar to WiFi, different charging policy on service via unlicensedband could be adopted depending on the operator's will. Charging policyincludes time-based, volume-based, event-based, free, and so on.Especially, volume-based charging shall be supported in case ofsupporting different charging policies. Lower price in unlicensed bandis reasonable since the spectrum is free. In RAN offloading, band usage(e.g. occupancy of licensed or unlicensed band) of each packet istransparent to the charging system located in CN. All packets via singlebearer (same QoS) will be charged equally now. In current operator'snetwork, the price of LTE data is always much higher than the price ofWiFi data (for example, almost free). LTE-U could provide a more stableQoS by utilizing the licensed band if the unlicensed band is busy;however, much more price (in LTE price) must be paid by the users thanWiFi if similar QoS/QoE can be provided by WiFi when there are only fewusers. On the other hand, eNB is less likely to provide LTE-U as cheapas WiFi due to the occupation of licensed band sometimes. Therefore, theprice of data volume in RAN offloading should be more dynamic based onband usage, which is beneficial to both users and operators.

SUMMARY

One non-limiting and exemplary embodiment provides a band usageinformation generating and reporting method to support differentcharging for data usage of different bands when traffic is offloaded inthe eNB.

In one general aspect, the techniques disclosed here feature a bandusage information generating and reporting method for wirelesscommunication performed by an eNB, comprising: generating band usageinformation for charging; and a reporting the band usage information toa core network (CN), wherein the band usage information involves bandusage of at least a first band and a second band, and traffic isassigned to respective bands by the eNB.

According to the present disclosure, the band usage informationinvolving band usage of different bands can be reported to the CN forprocessing the charging based on the band usage of the different bands.Therefore, the billing will be more accurate and reasonable.

It should be noted that general or specific embodiments may beimplemented as a system, a method, an integrated circuit, a computerprogram, a storage medium, or any selective combination thereof.

The foregoing is a summary and thus contains, by necessity,simplifications, generalization, and omissions of details. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matters described herein will become apparent in theteachings set forth herein. The summary is provided to introduce aselection of concepts in a simplified form that are further describedbelow in the Detailed Description. This summary is not intended toidentify key features or essential features of the claimed subjectmatter, nor is it intended to be used as an aid in determining the scopeof the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates RAN offloading of traffic, in which thetraffic is assigned to a LTE licensed band and a LTE unlicensed band atthe eNB;

FIG. 2 illustrates an exemplary wireless communication system comprisinga RAN and a CN for explaining the band usage information generating andreporting method according to an embodiment of the present disclosure;

FIG. 3 illustrates a flowchart of a band usage information generatingand reporting method for wireless communication performed by an eNBaccording to an embodiment of the present disclosure;

FIG. 4 illustrates a flowchart of a charging method for wirelesscommunication performed by a CN according to an embodiment of thepresent disclosure;

FIG. 5 schematically illustrates the initial setup of the reporting fromthe eNB to the MME in an embodiment of the present disclosure;

FIG. 6 schematically illustrates the reporting from the eNB to the MMEin an embodiment of the present disclosure;

FIG. 7 schematically illustrates the initial setup of the reporting fromthe eNB to the MME in an embodiment of the present disclosure;

FIG. 8 schematically illustrates the reporting from the eNB to the MMEin an embodiment of the present disclosure;

FIG. 9 schematically illustrates the initial setup of the reporting fromthe eNB to the MME in an embodiment of the present disclosure;

FIG. 10 schematically illustrates the reporting from the eNB to the MMEin an embodiment of the present disclosure;

FIG. 11 illustrates a flowchart of a band usage information generatingand reporting method for wireless communication performed by a UEaccording to an embodiment of the present disclosure; and

FIG. 12 illustrates a schematic block diagram of an eNB for generatingand reporting band usage information according to an embodiment of thepresent disclosure.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part thereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. It will be readily understood that the aspects ofthe present disclosure can be arranged, substituted, combined, anddesigned in a wide variety of different configurations, all of which areexplicitly contemplated and make part of this disclosure.

In the first aspect of the present disclosure, in particular, the bandusage information is reported to a packet data network gateway (PGW) viaa mobility management entity (MME) and a serving gateway (SGW) from theeNB.

In the first aspect of the present disclosure, in particular, the bandusage information reporting step comprises reporting the band usageinformation to the MME by S1-AP interface, wherein the initial setup forsupporting the reporting is performed by adding a new informationelement (IE) in an INITIAL CONTEXT SETUP REQUEST requested by the MME.

In the first aspect of the present disclosure, in particular, the bandusage information reporting step comprises reporting the band usageinformation to the MME by S1-AP interface, wherein the initial setup forsupporting the reporting is performed by adding a new IE in an E-RABSETUP REQUEST requested by the MME.

In the first aspect of the present disclosure, in particular, the bandusage information reporting step comprises reporting the band usageinformation to the MME by S1-AP interface, wherein the initial setup forsupporting the reporting is performed by adding a new IE in a S1 SETUPREQUEST requested by the eNB.

In the first aspect of the present disclosure, in particular, the bandusage information reporting step comprises reporting the band usageinformation to the MME by S1-AP interface, wherein a new IE is added ina UE CONTEXT MODIFICATION REQUEST requested by the MME to trigger thereporting, and a new IE is added in a UE CONTEXT MODIFICATION RESPONSEto report the band usage information to the MME.

In the first aspect of the present disclosure, in particular, the bandusage information reporting step comprises reporting the band usageinformation to the MME by S1-AP interface, wherein a new IE is added inan E-RAB MODIFIY REQUEST requested by the MME to trigger the reporting,and a new IE is added in an E-RAB MODIFY RESPONSE to report the bandusage information to the MME.

In the first aspect of the present disclosure, in particular, the bandusage information reporting step comprises reporting the band usageinformation to the MME by S1-AP interface, wherein a new IE is added toa CELL TRAFFIC TRACE triggered by the eNB to report the band usageinformation to the MME.

In the first aspect of the present disclosure, in particular, in theband usage information generating step, a counting entity at the PacketData Convergence Protocol (PDCP) layer counts band usage of all orsuccessfully received PDCP service data units (SDUs) for the first bandand the second band respectively to generate the band usage information.

In the first aspect of the present disclosure, in particular, innon-transparent mode radio link control (RLC), the band usageinformation generating step comprises: a counting entity at the mediumaccess control (MAC) layer reporting band usage state of each RLCprotocol data unit (PDU) to the RLC layer; a counting entity at the RLClayer deriving band usage state of each PDCP PDU based on the indicatedband usage state of corresponding RLC PDU(s) and reporting the bandusage state of each PDCP PDU to the PDCP layer; and the counting entityat the PDCP layer counting the band usage of all or successfullyreceived PDCP SDU(s) based on the indicated band usage state ofcorresponding PDCP PDU(s) to generate the band usage information.

In the first aspect of the present disclosure, in particular, intransparent mode RLC, the band usage information generating stepcomprises: a counting entity at the MAC layer reporting band usage stateof each RLC PDU to the PDCP layer; and a counting entity at the PDCPlayer counting the band usage of all or successfully received PDCPSDU(s) based on the indicated band usage state of corresponding RLCPDU(s) to generate the band usage information.

In the first aspect of the present disclosure, in particular, the bandusage information generating step further comprises: a counting entityat the PHY layer reporting band usage state of each MAC PDU to the MAClayer; and the counting entity at the MAC layer deriving the band usagestate of each RLC PDU based on the indicated band usage state ofcorresponding MAC PDU(s).

In the first aspect of the present disclosure, in particular, whilereporting the band usage state of each PDU, an ACK/NACK indicatorindicating whether the PDU is successfully received is also reported bythe counting entity of the corresponding layer, and the ACK/NACKindicator together with the band usage state of each PDU is used toderive the band usage state of the SDU corresponding to the PDU.

In the first aspect of the present disclosure, in particular, the bandusage state of each PDCP SDU is derived by CN marked priority of flow.

In the first aspect of the present disclosure, in particular, in theband usage information generating step, the counting entity at the PHYlayer counts band usage of all or successfully received transport blocks(TBs) for the first band and the second band respectively to generatethe band usage information.

In the first aspect of the present disclosure, in particular, in theband usage information generating step, the counting entity at the MAClayer counts band usage of all or successfully received MAC SDUs for thefirst band and the second band respectively to generate the band usageinformation.

In the first aspect of the present disclosure, in particular, in theband usage information generating step, the counting entity at the RLClayer counts band usage of all or successfully received RLC SDUs for thefirst band and the second band respectively to generate the band usageinformation, and the band usage state of each RLC SDU is derived fromthe PHY layer and/or the MAC layer.

In the first aspect of the present disclosure, in particular, the firstband is a licensed band; and the second band is an unlicensed band.

In the first aspect of the present disclosure, in particular, for dualconnectivity (DC) scenario of option 3C, in the band usage informationgenerating step, data packets via Xn will be all counted as the bandusage of one of the first band and the second band.

In the first aspect of the present disclosure, in particular, the bandusage information is respective data volume of the first band and thesecond band, data volume of the first band or the second band, bandusage ratio of the first band or the second band, or a reference ratebased on the band usage of the first band and the second band.

In the first aspect of the present disclosure, in particular, one validperiod for the band usage information is: time between last two triggerevents if the reporting of the band usage information is passivelytriggered by the CN; or time from last reporting to current reporting ifthe reporting of the band usage information is actively performed by theeNB; or time between two switch events between the first band and thesecond band.

In the first aspect of the present disclosure, in particular, the bandusage information generating and reporting method can further comprisetransmitting the band usage information to a UE for which the chargingis targeted.

In a second aspect of the present disclosure, there is provided acharging method for wireless communication performed by a core network(CN), comprising: a band usage information obtaining step of obtainingband usage information for charging from an eNB; and a chargingprocessing step of processing the charging based on the band usageinformation, wherein the band usage information involves band usage ofat least a first band and a second band, and traffic is assigned torespective bands by the eNB.

In the second aspect of the present disclosure, in particular, the CNcomprises at least a MME, a SGW and a PGW, and in the band usageinformation obtaining step, the band usage information reported from theeNB is first received by the MME, and then reported to the PGW via theSGW by the MME.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises the MME receiving the bandusage information reported from the eNB by S1-AP interface, wherein theinitial setup for supporting the reporting is performed by adding a newinformation element (IE) in an INITIAL CONTEXT SETUP REQUEST requestedby the MME.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises the MME receiving the bandusage information reported from the eNB by S1-AP interface, wherein theinitial setup for supporting the reporting is performed by adding a newIE in an E-RAB SETUP REQUEST requested by the MME.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises the MME receiving the bandusage information reported from the eNB by S1-AP interface, wherein theinitial setup for supporting the reporting is performed by a new IE in aS1 SETUP REQUEST requested by the eNB.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises the MME receiving the bandusage information reported from the eNB by S1-AP interface, wherein anew IE is added in a UE CONTEXT MODIFICATION REQUEST requested by theMME to trigger the reporting, and a new IE is added in a UE CONTEXTMODIFICATION RESPONSE to report the band usage information to the MME.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises the MME receiving the bandusage information reported from the eNB by S1-AP interface, wherein anew IE is added in an E-RAB MODIFIY REQUEST requested by the MME totrigger the reporting, and a new IE is added in an E-RAB MODIFY RESPONSEto report the band usage information to the MME.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises the MME receiving the bandusage information reported from the eNB by S1-AP interface, wherein anew IE is added to a CELL TRAFFIC TRACE triggered by the eNB to reportthe band usage information to the MME.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises reporting the band usageinformation from the MME to the SGW or from the SGW to the PGW by addinga new IE in a BEARER CONTEXT TO BE MODIFIED WITHIN MODIFY BEARERREQUEST.

In the second aspect of the present disclosure, in particular, the bandusage information obtaining step comprises reporting the band usageinformation from the MME to the SGW or from the SGW to the PGW by addinga new IE in a BEARER CONTEXT WITHIN UPDATE BEARER REQUEST for triggeringand adding a new IE in a BEARER CONTEXT WITHIN UPDATE BEARER RESPONSEfor reporting.

In the second aspect of the present disclosure, in particular, the firstband is a licensed band; and the second band is an unlicensed band.

In the second aspect of the present disclosure, in particular, in thecharging processing step, for a pre-pay user, units in the licensed bandare firstly reserved or blocked, then over-reserved units are returnedto the user's account based on the band usage information; and for apost-pay user, a bill will be generated based on the band usageinformation.

In a third aspect of the present disclosure, there is provided a bandusage information generating and reporting method for wirelesscommunication performed by a UE, comprising: a band usage informationgenerating step of generating band usage information for charging; and aband usage information reporting step of reporting the band usageinformation to a core network (CN) by Non-Access Stratum (NAS), whereinthe band usage information involves band usage of at least a first bandand a second band, and traffic is assigned to respective bands by an eNBto which the UE is attached.

In a fourth aspect of the present disclosure, there is provided an eNodeB (eNB) for generating and reporting band usage information for wirelesscommunication, comprising: a band usage information generating unitconfigured to generate band usage information for charging; and a bandusage information reporting unit configured to report the band usageinformation to a core network (CN), wherein the band usage informationinvolves band usage of at least a first band and a second band, andtraffic is assigned to respective bands by the eNB.

In a fifth aspect of the present disclosure, there is provided a corenetwork (CN) for processing charging for wireless communication,comprising: a band usage information obtaining unit configured to obtainband usage information for charging from an eNB; and a chargingprocessing unit configured to process the charging based on the bandusage information, wherein the band usage information involves bandusage of at least a first band and a second band, and traffic isassigned to respective bands by the eNB.

In a sixth aspect of the present disclosure, there is provided amobility management entity (MME) for communicating band usageinformation for wireless communication, comprising: a band usageinformation receiving unit configured to receive band usage informationfor charging from an eNB; and a band usage information reporting unitconfigured to report the band usage information to a PGW via a SGW,wherein the band usage information involves band usage of at least afirst band and a second band, and traffic is assigned to respectivebands by the eNB.

In a seventh aspect of the present disclosure, there is provided a userequipment (UE) for generating and reporting band usage information forwireless communication, comprising: a band usage information generatingunit configured to generate band usage information for charging; and aband usage information reporting unit configured to report the bandusage information to a core network (CN) by Non-Access Stratum (NAS),wherein the band usage information involves band usage of at least afirst band and a second band, and traffic is assigned to respectivebands by an eNB to which the UE is attached.

It is noted that the above specific descriptions for the first aspectand the second aspect can also be applied to the third to seventhaspects unless the context indicates otherwise.

Based on current CN architecture, single service data flow (via singleEPS (Evolved Packet System) bearer) could support RAN offloading (forexample, DL (Down Link)). However, there are following problems: 1) Nodistinction between data via unlicensed and licensed band in price. 2)To operator, an average price between unlicensed and licensed pricemight be accounted for bearer supporting both unlicensed and licensedband based on statistics; however, this is infeasible due to unawarenessof band usage at CN. 3) Even if average price could be supportedsomehow, to a specific user who has more data volumes via unlicensedband, the actually payment would remain unchanged. Such charging policyis not good motivation for promoting more utilization of unlicensed bandwhen possible. Price on utilization of unlicensed band should be cheaperthan utilization of licensed band, similar to that WiFi price is muchcheaper than LTE currently. Therefore, separately counting for datavolume via licensed band and data volume via unlicensed band isnecessary for a UE working at both bands.

In order to charge data volume via a licensed band and an unlicensedband separately, band usage information for charging involving bandusage of the two bands should be reported to a charging system in theCN. In other words, the CN has to know the data volume of differentbands separately. It is noted that, although some embodiments may bedescribed in the context of licensed band and unlicensed band as twobands to be charged separately, the two bands are not limited to thelicensed and unlicensed bands but can be any two different bands thatcan be used for wireless communication, which are generally referred toa first band and a second band in the present disclosure.

In present disclosure, it is proposed that the band usage information isgenerated at RAN (eNB or UE), and is reported to the CN via a RAN/CNinterface. Since the traffic is assigned to different bands at the eNB,the eNB and the UE can know which data uses which band based on thescheduling information. There could be two reporting mechanisms forreporting the band usage information to the CN. One is active reportingtriggered by the eNB which can be periodical and/or event-triggered. Theother is passive reporting triggered by CN (e.g. via PCEF (Policy andCharging Enforcement Function)) which can also be periodical and/orevent-triggered.

FIG. 2 illustrates an exemplary wireless communication system comprisinga RAN and a CN for explaining the band usage information generating andreporting method according to an embodiment of the present disclosure.In FIG. 2, the RAN comprises an eNB and a UE, and the CN comprises atleast a MME, a SGW and a PGW. The CN can also comprise other element(s)for locating for example PCRF (Policy and Charging Rules Function),charging system, billing domain, and so on. According to the presentdisclosure, the band usage information can be generated at the eNB orthe UE, can then reported to the CN, for example, to the PGW in whichPCEF is located via the MME and the SGW. The band usage informationobtained by the PGW will be used to process charging by a chargingsystem located in the CN.

As described in the above, there may be two types of offloading (CNoffloading and RAN offloading). As an example, the procedure ofoffloading initialization can be as follows:

1) Bearer establishment procedure

-   -   a) Step-1: UE could request one service via only unlicensed band        or both unlicensed and licensed band based on capability and        subscription. Here, traditional service specific to licensed        band is not affected.    -   b) Step-2: PCRF could request to establish the bearer(s)        according to UE request and subscription.    -   c) Step-3: eNB could establish bearer at unlicensed or licensed        band or both as request from CN.        2) Perform offloading    -   a) eNB performs RAN offloading between a first band and a second        band (e.g. a licensed and an unlicensed band) for bearer not        specific to unlicensed band based on channel condition and        traffic load (e.g. priority/preference/marking of        service/packet/user indicated from CN).    -   b) Or CN offloads the traffic to unlicensed bearer.

Specifically, each step at the bearer establishment procedure can beexemplarily described in detail as follows:

1) UE's decision at Step-1

-   -   a) UE supporting RAN offloading would request a bearer not        specific to unlicensed band (RAN offloading) if        -   i) UE subscribes RAN offloading service,        -   ii) Or UE manually selects RAN offloading,        -   iii) Or the like.    -   b) Otherwise, UE would request a bearer specific to unlicensed        band (CN offloading).        2) PCRF's decision at step-2    -   a) PCRF would request to establish a bearer not specific to        unlicensed band (RAN offloading) if        -   i) UE requests a bearer not specific to unlicensed band, and            UE subscribes RAN offloading service,        -   ii) Or the like.

b) Otherwise, PCRF would request to establish a bearer specific tounlicensed band (CN offloading).

3) eNB's decision at Step-3

-   -   a) eNB would establish a bearer not specific to unlicensed band        (RAN offloading) if        -   i) PCRF requests to establish a bearer not specific to            unlicensed band, and eNB supports RAN offloading,        -   ii) Or the like.        -   Optionally, SeNB (Secondary eNB) in unlicensed band would            establish the unlicensed radio bearer in case of DC            option-1.        -   Then, eNB would offload partial/entire data to unlicensed            band during transmission if        -   i) Unlicensed band is idle,        -   ii) Or unlicensed band can meet the QoS requirement,        -   iii) Or licensed band is heavily loaded,        -   iv) Or CN indicates priority/preference/marking of            service/flow/packet/user        -   v) Or the like    -   b) Otherwise, eNB would establish a bearer specific to        unlicensed band (CN offloading).

In particular, in the procedure of offloading initialization, UE couldrequest a lower QoS than actually needed QoS for easier acceptance byCN, which is beneficial to licensed band under high load. Lower pricewill be applied for lower QoS. To meet the actually needed QoS,unlicensed band can be used if available.

For RAN offloading case, traffic is assigned to a first band (e.g.licensed band) and/or a second band (e.g. unlicensed band) at the eNB.Therefore, the CN does not know which band(s) the traffic uses.According to an embodiment of the present disclosure, the eNB generatesthe band usage information involving two bands and reports it to the CN.FIG. 3 illustrates a flowchart of a band usage information generatingand reporting method 300 for wireless communication performed by an eNBaccording to an embodiment of the present disclosure. The method 300comprises a band usage information generating step 301 of generatingband usage information for charging; and a band usage informationreporting step 302 of reporting the band usage information to a CN. Inthis embodiment, traffic is assigned to respective bands by the eNB,that is, it is RAN offloading. The band usage information involves bandusage of at least a first band and a second band, for example, alicensed band and an unlicensed band. It is noted that although thefollowing embodiments may be described for the first band and the secondband, there can be more than two bands involved in the presentdisclosure. The band usage information can be any form of informationthat can be used by the CN to process the charging. For example, theband usage information can be respective data volume of the first bandand the second band, that is, the band usage information comprises boththe data volume consuming the first band and the data volume consumingthe second band, for example, 1 MB (Mega Byte) for the first band and 2MB for the second band. Alternatively, the band usage information cancomprise only data volume of one band of the first band and the secondband. In this case, the data volume of the other band can be derived bysubtracting the data volume of the one band from the total data volumeat the CN side. Alternatively, the band usage information can be theband usage ratio (0˜100%) of the first band or the second band, forexample, the data volume using one (e.g. unlicensed band) of the firstband and the second band is 70% of the total volume. In this case, theCN side can calculate a price or discount based on the band usage ratio.As another alternative, the band usage information can be a referencerate (e.g. 10 dollars) based on the band usage of the first band and thesecond band. The reference rate can be derived for example bymultiplying a reference unit price by the band usage of the first bandand the second band respectively. Further, the band usage informationcan be generated per IP flow, per bear ID, per UE, per cell, or per eNB.

Accordingly, at the CN side, a charging method for wirelesscommunication can be provided. FIG. 4 illustrates a flowchart of acharging method 400 for wireless communication performed by a CN. Themethod 400 comprises a band usage information obtaining step 401 ofobtaining band usage information for charging from an eNB and a chargingprocessing step 402 of processing the charging based on the band usageinformation, wherein the band usage information involves band usage ofat least a first band and a second band, and traffic is assigned torespective bands by the eNB. As shown in FIG. 2, the CN can comprise atleast a MME, a SGW and a PGW, and the band usage information reportedfrom the eNB can be first received by the MME, and then reported to thePGW via the SGW by the MME. The charging processing step 402 can beperformed by a charging system in the CN. For example, for a pre-payuser, units in the licensed band can be firstly reserved or blocked,then over-reserved units are returned to the user's account based on theband usage information; and for a post-pay user, a bill can be generatedbased on the band usage information. It is noted that the specificmanners of processing the charging based on the band usage informationdo not limit the scope of the disclosure, but those skilled in the artcan devise various manners to process the charging depending onpractical applications.

In the following, the band usage information generating step 301 will bedescribed in detail through embodiments.

In a first embodiment, a counting entity at the Packet Data ConvergenceProtocol (PDCP) layer counts band usage of all or successfully receivedPDCP service data units (SDUs) for the first band and the second bandrespectively to generate the band usage information. In this embodiment,the band usage information is generated at the PDCP layer, and thus theband usage of PDCP SDUs (i.e. IP packets) can be counted. Therefore, theoverhead (e.g. header and control PDUs) can be excluded. In thisembodiment, the counting entity may count all PDCP SDUs whether they arereceived successfully. Alternatively, the counting entity may only countsuccessfully received PDCP SDUs while omitting PDCP SDUs that are notsuccessfully received. Herein, the “successfully received SDU or PDU”means that the eNB has successfully received the SDU or PDU for theuplink, and the eNB has successfully received ACK feedback of the SDU orPDU for the downlink. Regarding data forwarded by source eNB in case oflossless handover, the same counting criteria can be adopted as the datais from the CN. Preferably, forwarded data during lossless handover willbe counted only once.

As a first example of the first embodiment, starting from the PHY layer,each layer reports its band usage state to its upper layer, and thecounting entity at the PDCP layer counts the band usage of PDCP SDUsbased on the band usage state of the RLC layer. In particular, acounting entity at the PHY layer reports band usage state of each MACPDU to the MAC layer; a counting entity at the MAC layer derives theband usage state of each RLC PDU based on the indicated band usage stateof corresponding MAC PDU(s) and reports the band usage state of each PLCPDU to the RLC layer; a counting entity at the RLC layer derives bandusage state of each PDCP PDU based on the indicated band usage state ofcorresponding RLC PDU(s) and reports the band usage state of each PDCPPDU to the PDCP layer; and the counting entity at the PDCP layercounting the band usage of all or successfully received PDCP SDU(s)based on the indicated band usage state of corresponding PDCP PDU(s) togenerate the band usage information.

The PHY layer can obtain the band usage state of each MAC PDU (TB) whichindicates which band the TB uses from the scheduling information. Afterthe band usage state of each MAC PDU is reported to the MAC layer, theMAC layer can derive the band usage state of each RLC PDU (MAC SDU)based on the indicated band usage state of corresponding MAC PDU(s). Itis noted that MAC SDUs and MAC PDUs may not be in a one-to-onerelationship. For example, one MAC SDU may be split into several MACPDUs, or several MAC SDUs may be combined into one or more MAC PDUs.Therefore, the band usage state of a MAC SDU may indicate whatpercentage of the MAC SDU uses the first band or the second band. Forexample, if one MAC SDU is split into two MAC PDUs and one of the MACPDUs is scheduled at the first band, then the band usage state of theMAC SDU can indicate that 50% of the MAC SDU uses the first band.Alternatively, the band usage state of the MAC SDU can be rounded. Forexample, if no less than half of the MAC SDU uses the first band, theband usage state of the MAC SDU indicates that the MAC SDU uses thefirst band. In the above example, 50% of the MAC SDU uses the firstband, and thus the band usage state of the MAC SUD can be rounded toindicate that the MAC SDU uses the first band. In addition, the bandusage state of a MAC SDU may also be a percentage or a rounded statebecause there may be retransmissions (HARQ processes) of MAC PDUs. Forexample, a MAC PDU may be transmitted first in the unlicensed band in afirst HARQ process but the transmission does not succeed, and then a MACPDU corresponding to the same MAC SDU is transmitted in the licensedband in a first HARQ process and the transmission succeeds. In thiscase, if both the successful and unsuccessful HARQ processes areconsidered, the band usage state of the MAC SDU should indicate 50% ofthe MAC SDU uses the licensed (or unlicensed) band. Alternatively, ifonly the successful HARQ process is considered, the band usage state ofthe MAC SDU should indicate the MAC SDU uses the licensed band. Afterthe band usage state of each RLC PDU (MAC SDU) is reported to the RLClayer, the RLC layer can derive band usage state of each PDCP PDU basedon the indicated band usage state of corresponding RLC PDU(s). Similarto the band usage state of the RLC PDU, the band usage state of the PDCPPDU can also be a percentage or a rounded state since there can be ARQprocesses, segmentation and/or concatenation for the RLC layer. Afterthe band usage state of each PDCP PDU is reported to the PDCP layer, thePDCP layer can derive band usage state of each PDCP SDU (IP packet), andcount the band usage of the PDCP SDU(s) for the first band and thesecond band respectively.

The above first example is for the non-transparent mode RLC. In thetransparent mode RLC as a second example, the counting at the RLC layercan be omitted. In particular, the counting entity at the MAC layerreports band usage state of each RLC PDU directly to the PDCP layer; andthe counting entity at the PDCP layer counts the band usage of all orsuccessfully received PDCP SDU(s) based on the indicated band usagestate of corresponding RLC PDU(s) to generate the band usageinformation.

In addition, since the MAC layer at eNB can know the band usage state ofeach MAC SDU from the band scheduling of the MAC SDU, the reporting ofthe PHY layer can be omitted. Therefore, in a third example, on thebasis of the first and the second examples, the steps of a countingentity at the PHY layer reporting band usage state of each MAC PDU tothe MAC layer and a counting entity at the MAC layer deriving the bandusage state of each RLC PDU based on the indicated band usage state ofcorresponding MAC PDU(s) are omitted. Instead, the counting entity atthe MAC layer reports band usage state of each RLC PDU (MAC SDU) whichis derived from band scheduling of the MAC SDU to the RLC layer.

In the above first to third examples, preferably, while reporting theband usage state of each PDU, an ACK/NACK indicator indicating whetherthe PDU is successfully received is also reported by the counting entityof the corresponding layer, and the ACK/NACK indicator together with theband usage state of each PDU is used to derive the band usage state ofthe SDU corresponding to the PDU. Here, the “PDU” can refer to any ofMAC PDU, RLC PDU and PDCP PDU. According to this preferable example, thecounting entity can determine whether a PDU is successfully received.Therefore, when the counting entity derives the band usage state of theSDU corresponding to the PDU, it can consider all PDU(s) related to theSDU or consider only successfully received PDU(s). In other words,retransmission (e.g. HARQ process in the MAC layer and ARQ process inthe RLC layer) can be considered here. As described in the above, in theMAC layer, there can be HARQ processes of MAC PDUs, and when determiningthe band usage state of a MAC SDU, all the HARQ processes can beconsidered or only the successful HARQ process is considered. In the RLClayer, there can be ARQ processes of PLC PDUs, and when determining theband usage state of a PLC SDU, all the ARQ processes can be consideredor only the successful ARQ process is considered. Accordingly, thecounting entity at the PDCP layer can count the band usage of all orsuccessfully received PDCP SDU(s) based on the indicated band usagestate and ACK/NACK indicator of corresponding PDCP PDU(s).

In a fourth example of the first embodiment, the band usage of each PDCPSDU can be derived by CN marked priority of flow, instead of reported bya lower layer. For example, the band usage in terms of ratio can bederived from CN marked priority level e.g. level 1=10%, level 2=20%, . .. , level 9=90%. The RAN offloading criteria can be based on CNindicated priority/marking. A User Plane CONgestion management (UPCON)related mechanism where the GGSN/PGW/TDF marks each user plane datapacket delivered in the downlink direction might be adopted as RANoffloading criteria. The marking is meant to support trafficprioritization between flows mapped to the same QCI, i.e. different IPflows within a bearer may be associated with different values of themarking in order to address RAN User Plane congestion, thus the flowswith lower prioritization would be offloaded to unlicensed band ifcongestion happens in licensed band.

In the above first embodiment, the band usage information is generatedat the PDCP layer. However, the band usage information can also begenerated at other layers, i.e. the PHY layer, the MAC layer, or the RLClayer.

In a second embodiment, the counting entity at the PHY layer can countband usage of all or successfully received transport blocks (TBs) forthe first band and the second band respectively to generate the bandusage information. In this case, the band usage information can indicatethe band usage of PHY data to the CN. Preferably, in order to reducespecification impact as well as counting inaccuracy, the PHY layer cancount the relative ratio of band usage for the first band and the secondband as the band usage information.

In a third embodiment, the counting entity at the MAC layer can countband usage of all or successfully received MAC SDUs for the first bandand the second band respectively to generate the band usage information.In this case, the band usage information can indicate the band usage ofMAC data to the CN. Preferably, in order to reduce specification impactas well as counting inaccuracy, the MAC layer can count the relativeratio of band usage for all or successfully received MAC SDUs. Inparticular, the MAC layer first counts data volume of all orsuccessfully received MAC PDUs separately according to the scheduledband (the first band or the second band), e.g. 1 k bit via licensed bandand 2 k bit via unlicensed band for an observation period. Then, thecounting entity at the MAC layer generates the ratio of the first orsecond band data volume (e.g. unlicensed data volume) to the total datavolume. Since percentage of overhead and higher layer retransmissionwill be equal between MAC PDUs via the unlicensed band and MAC PDUs viathe licensed bands in statistics, the ratio observed over a longerperiod is less impacted by over counting than data volume observed overthe period. For example, the ratio may be 2 k/(1 k+2 k=0.67≈70% whichcan be represented by 4 bit. After the band usage ratio as the bandusage information is generated, it can be reported to the CN in a mannertransparent to RLC and PDCP.

In a fourth embodiment, the counting entity at the RLC layer can countband usage of all or successfully received RLC SDUs for the first bandand the second band respectively to generate the band usage information,and the band usage state of each RLC SDU can be derived from the PHYlayer and/or the MAC layer. Preferably, in order to reduce specificationimpact as well as counting inaccuracy, the RLC layer can count therelative ratio of band usage for the first band and the second band asthe band usage information.

In the above first to fourth embodiment, the basic application scenariois carrier aggregation. In a fifth embodiment, for dual connectivityscenario (DC) of option 3C (refer to 3GPP TR 36.842, Study on Small Cellenhancements for E-UTRA and E-UTRAN; Higher layer aspects), data packetsvia Xn can be all counted as the band usage of one of the first band andthe second band, for example, the unlicensed band. Then countingprocedure would be that the PDCP layer counts the data volume of PDCPSDUs separately according to Xn separation.

In the above, the band usage information generating step is described indetail by embodiments. After the band usage information is generated, itcan be reported to the CN. In addition, the band usage information canalso be transmitted to a UE for which the charging is targeted. In thiscase, the UE can know its band usage status.

In the following, the band usage information reporting step 302 by theeNB and the band usage information obtaining step 401 by the CN will bedescribed in detail by embodiments, in which the band usage informationis first reported from the eNB to the MME by S1-AP interface asspecified in TS 36.413 (refer to 3GPP TS36.413:S1 Application Protocol(S1AP)). Before actually reporting the band usage information from theeNB to the MME, the initial setup for supporting the reporting should beperformed.

In a sixth embodiment, the band usage information can be reported in aContext Management procedure of S1-MME (S1-AP in TS 36.413) interface.If both the eNB and the UE support the two band operation (e.g. LTE-U)based on INITIAL UE MESSAGE, the initial setup for supporting thereporting can be performed by adding a new IE in an INITIAL CONTEXTSETUP REQUEST requested by the MME. Here, a new IE can be added for allE-RABs or added for certain E-RAB(s). Table 1 illustrates the INITIALCONTEXT SETUP REQUEST added with a new IE (Unlicensed Band Operation)for all E-RABs and/or a certain E-RAB.

TABLE 1 INITIAL CONTEXT SETUP REQUEST IE type and Semantics AssignedIE/Group Name Presence Range reference description CriticalityCriticality Message Type M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3YES reject eNB UE S1AP ID M 9.2.3.4 YES reject UE Aggregate Maximum M9.2.1.20 YES reject Bit Rate E-RAB to Be Setup List 1 YES reject >E-RABto Be Setup 1 . . . <maxnoofE- EACH reject Item IEs RABs> >>E-RAB ID M9.2.1.2 — >>E-RAB Level QoS M 9.2.1.15 Includes — Parameters necessaryQoS parameters. >>Transport Layer M 9.2.2.1 — Address >>GTP-TEID M9.2.2.2 — >>NAS-PDU O 9.2.3.5 — >>Correlation ID O 9.2.1.80 YESignore >>Unlicensed O ENUMERATED YES ignore Band Operation (true) UESecurity Capabilities M 9.2.1.40 YES reject Security Key M 9.2.1.41 TheKeNB is YES reject provided after the key- generation in the MME, see TS33.401 [15]. Trace Activation O 9.2.1.4 YES ignore Handover RestrictionList O 9.2.1.22 YES ignore UE Radio Capability O 9.2.1.27 YES ignoreSubscriber Profile ID for O 9.2.1.39 YES ignore RAT/Frequency priorityCS Fallback Indicator O 9.2.3.21 YES reject SRVCC Operation O 9.2.1.58YES ignore Possible CSG Membership Status O 9.2.1.73 YES ignoreRegistered LAI O 9.2.3.1 YES ignore GUMMEI O 9.2.3.9 This IE YES ignoreindicates the MME serving the UE. MME UE S1AP ID 2 O 9.2.3.3 This IE YESignore indicates the MMEUE S1AP ID assigned by the MME. Management BasedMDT O 9.2.1.83 YES ignore Allowed Management Based MDT O MDT PLMN ListYES ignore PLMN List 9.2.1.89 Unlicensed Band O ENUMERATED YES ignoreOperation (true)

In Table 1, a new IE (Unlicensed Band Operation) which is underlined isadded for the UE (all E-RABs) and/or a certain E-RAB. It is noted thatthe name of the IE is only an example. When performing the initialsetup, the MME can send the INITIAL CONTEXT SETUP REQUEST added with thenew IE to the eNB, and the eNB may feedback an INITIAL CONTEXT SETUPCOMPLETE to the MME, as shown in FIG. 5 which schematically illustratesthe initial setup of the reporting in this embodiment.

After the initial setup is completed, the band usage information can bereported from the eNB to the MME. In this embodiment, the reporting canbe triggered by the MME in a UE Context Modification procedure. As shownin FIG. 6, the MME sends a UE CONTEXT MODIFICATION REQUEST to the eNB totrigger the reporting, and the eNB feedbacks a UE CONTEXT MODIFICATIONRESPONSE with the band usage information to the MME. In particular, anew IE can be added in the UE CONTEXT MODIFICATION REQUEST requested bythe MME to trigger the reporting, and a new IE can be added in the UECONTEXT MODIFICATION RESPONSE to report the band usage information tothe MME. Here, the triggering and reporting can be performed for the UE(all E-RABs) and/or certain E-RAB(s). Table 2 illustrates the UE CONTEXTMODIFICATION REQUEST added with a new IE (Band Usage Query) for allE-RABs and/or a certain E-RAB.

TABLE 2 UE CONTEXT MODIFICATION REQUEST IE type and Semantics AssignedIE/Group Name Presence Range reference description CriticalityCriticality Message Type M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3YES reject eNB UE S1AP ID M 9.2.3.4 YES reject Security Key O 9.2.1.41 Afresh KeNB is YES reject provided after performing a key- change on thefly procedure in the MME, see TS 33.401 [15]. Subscriber Profile ID forO 9.2.1.39 YES ignore RAT/Frequency priority UE Aggregate O 9.2.1.20 YESignore Maximum Bit Rate CS Fallback Indicator O 9.2.3.21 YES reject UESecurity Capabilities O 9.2.1.40 YES reject CSG Membership Status O9.2.1.73 YES ignore Registered LAI O 9.2.3.1 YES ignore E-RAB to BeQuery O 1 YES ignore List >E-RAB to Be O 1 . . . <maxnoofE- EACH ignoreQuery Item IEs RABs> >>E-RAB ID O 9.2.1.2 — >>Band Usage O ENUMERATEDYES ignore Query (true) Band Usage Query O ENUMERATED YES ignore (true)

In Table 2, a new IE (Band Usage Query) which is underlined is added forthe UE (all E-RABs) and/or a certain E-RAB. It is noted that the name ofthe IE is only an example. After the MME sends the UE CONTEXTMODIFICATION REQUEST added with Band Usage Query, the eNB can feedback aUE CONTEXT MODIFICATION RESPONSE with a new IE (e.g. Band Usage Report)to report the band usage information to the MME. Table 3 illustrates theUE CONTEXT MODIFICATION RESPONSE added with a new IE (Band Usage Report)for the UE (all E-RABs) and/or a certain E-RAB, in which the new IE isunderlined. In Table 3, the “IE type and reference” of “Band UsageReport” is defined as “ratio”, and the “Semantics description” is“Unlicensed band to licensed band”. In other words, in this example, theband usage information indicates the ratio of the band usage of theunlicensed band to the band usage of the licensed band. However, it isobvious that this form of the band usage information is only an example,and the band usage information herein can adopt any other suitable form.

TABLE 3 UE CONTEXT MODIFICATION RESPONSE IE type and Semantics AssignedIE/Group Name Presence Range reference description CriticalityCriticality Message Type M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3YES ignore eNB UE S1AP ID M 9.2.3.4 YES ignore Criticality Diagnostics O9.2.1.21 YES ignore E-RAB to Be Report O 1 YES ignore List >E-RAB to O 1. . . <maxnoofE- EACH ignore Be Report Item IEs RABs> >>E-RAB ID O9.2.1.2 — >>Band O Ratio Unlicensed YES ignore Usage Report band tolicensed band Band Usage Report O Ratio Unlicensed YES ignore band tolicensed band

In a seventh embodiment, the band usage information can be reported inan E-RAB Management procedure of S1-MME (S1-AP in TS 36.413) interface.If both the eNB and the UE support two band operation (e.g. LTE-U) basedon INITIAL UE MESSAGE, the initial setup for supporting the reportingcan be performed by adding a new IE in an E-RAB SETUP REQUEST requestedby the MME. Here, a new IE can be added for the UE (all E-RABs) or addedfor certain E-RAB(s). Table 4 illustrates the E-RAB SETUP REQUEST addedwith a new IE (Unlicensed Band Operation) for all E-RABs and/or acertain E-RAB.

TABLE 4 E-RAB SETUP REQUEST IE type and Semantics Assigned IE/Group NamePresence Range reference description Criticality Criticality MessageType M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3 YES reject eNB UES1AP ID M 9.2.3.4 YES reject UE Aggregate O 9.2.1.20 YES reject MaximumBit Rate E-RAB to be Setup 1 YES reject List >E-RAB To Be 1 . . .<maxnoofE- EACH reject Setup Item IEs RABs> >>E-RAB ID M 9.2.1.2— >>E-RAB Level M 9.2.1.15 Includes — QoS Parameters necessary QoSparameters. >>Transport Layer M 9.2.2.1 — Address >>GTP-TEID M 9.2.2.2EPC TEID. — >>NAS-PDU M 9.2.3.5 — >>Correlation ID O 9.2.1.80 YES ignore>>Unlicensed O ENUMERATED YES ignore Band Operation (true)Unlicensed Band O ENUMERATED YES ignore Operation (true)

In Table 4, a new IE (Unlicensed Band Operation) which is underlined isadded for the UE (all E-RABs) and/or a certain E-RAB. It is noted thatthe name of the IE is only an example. When performing the initialsetup, the MME can send the E-RAB SETUP REQUEST added with the new IE tothe eNB, and the eNB may feedback an E-RAB SETUP COMPLETE to the MME, asshown in FIG. 7 which schematically illustrates the initial setup of thereporting in this embodiment.

After the initial setup is completed, the band usage information can bereported from the eNB to the MME. In this embodiment, the reporting canbe triggered by the MME in an E-RAB Modify procedure. As shown in FIG.8, the MME sends an E-RAB MODIFY REQUEST to the eNB to trigger thereporting, and the eNB feedbacks an E-RAB MODIFY RESPONSE with the bandusage information to the MME. In particular, a new IE can be added in anE-RAB MODIFY REQUEST requested by the MME to trigger the reporting, anda new IE can be added in an E-RAB MODIFY RESPONSE to report the bandusage information to the MME. Here, the triggering and reporting can beperformed for all E-RABs and/or certain E-RAB(s). Table 5 illustratesthe E-RAB MODIFY REQUEST added with a new IE (Band Usage Query) for allE-RABs and/or a certain E-RAB.

TABLE 5 E-RAB MODIFY REQUEST IE type and Semantics Assigned IE/GroupName Presence Range reference description Criticality CriticalityMessage Type M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3 YES rejecteNB UE M 9.2.3.4 YES reject S1AP ID UE Aggregate O 9.2.1.20 YES rejectMaximum Bit Rate E-RAB to be 1 YES reject Modified List >E-RAB To Be 1 .. . <maxnoofE- EACH reject Modified Item IEs RABs> >>E-RAB ID M 9.2.1.2— >>E-RAB Level M 9.2.1.15 Includes — QoS Parameters necessary QoSparameters. >>NAS-PDU M 9.2.3.5 — >>Band O ENUMERATED YES ignoreUsage Query (true) Band Usage Query O ENUMERATED YES ignore (true)

In Table 5, a new IE (Band Usage Query) which is underlined is added forthe UE (all E-RABs) and/or a certain E-RAB. It is noted that the name ofthe IE is only an example. After the MME sends the E-RAB MODIFY REQUESTadded with Band Usage Query, the eNB can feedback an E-RAB MODIFYRESPONSE with a new IE (e.g. Band Usage Report) to report the band usageinformation to the MME. Table 6 illustrates the E-RAB MODIFY RESPONSEadded with a new IE (Band Usage Report) for all E-RABs and/or a certainE-RAB, in which the new IE is underlined. In Table 6, the “IE type andreference” of “Band Usage Report” is defined as “ratio”, and the“Semantics description” is “Unlicensed band to licensed band”. In otherwords, in this example, the band usage information indicates the ratioof the band usage of the unlicensed band to the band usage of thelicensed band. However, it is obvious that this form of the band usageinformation is only an example, and the band usage information hereincan adopt any other suitable form.

TABLE 6 E-RAB MODIFY RESPONSE IE type and Semantics Assigned IE/GroupName Presence Range reference description Criticality CriticalityMessage Type M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3 YES ignoreeNB UE S1AP ID M 9.2.3.4 YES ignore E-RAB Modify 0 . . . 1 YES ignoreList >E-RAB Modify 1 . . . <maxnoofE- EACH ignore Item IEs RABs> >>E-RABID M 9.2.1.2 — >>Band O Ratio Unlicensed YES ignore Usage Report band tolicensed band E-RAB Failed to O E-RAB List A value for E- YES ignoreModify List 9.2.1.36 RAB ID shall only be present once in E-RAB ModifyList IE + E-RAB Failed to Modify List IE. Criticality O 9.2.1.21 YESignore Diagnostics Band Usage O Ratio Unlicensed YES ignore Report bandto licensed band

It is noted that the initial setup procedures and the reportingprocedures in the sixth embodiment and the seventh embodiment can beexchanged. In addition, other initial setup procedures and reportingprocedures can also be applied, and all those initial setup proceduresand reporting procedures can be combined arbitrarily. Particularly, theinitial setup may not be needed for the reporting according to theimplementation of the eNB and the CN.

In an eight embodiment, another initial setup procedure is provided. Inthis embodiment, the initial setup is requested by the eNB. Inparticular, the initial setup for supporting the reporting is performedby adding a new IE in a S1 SETUP REQUEST requested by the eNB. Table 7illustrates the S1 SETUP REQUEST added with a new IE (Unlicensed BandOperation).

TABLE 7 S1 SETUP REQUEST IE type and Semantics Assigned IE/Group NamePresence Range reference description Criticality Criticality MessageType M 9.2.1.1 YES reject Global eNB ID M 9.2.1.37 YES reject eNB Name OPrintableString YES ignore (1 . . . 150, . . .) Supported TAs 1 . . .<maxnoofTACs> Supported GLOBAL reject TAs in the eNB. >TAC M 9.2.3.7Broadcasted — TAC. >Broadcast 1 . . . <maxnoofBPLMNs> Broadcasted —PLMNs PLMNs. >>PLMN M 9.2.3.8 Identity Default Paging DRX M 9.2.1.16 YESignore CSG Id List 0 . . . 1 GLOBAL reject >CSG Id M 1 . . .<maxnoofCSGIds> 9.2.1.62 Unlicensed Band O ENUMERATED YES ignoreOperation (true)

In Table 7, a new IE (Band Usage Report) which is underlined is added.It is noted that the name of the IE is only an example. When performingthe initial setup, the eNB can send the S1 SETUP REQUEST added with thenew IE to the MME, and the MME may feedback a S1 SETUP COMPLETE to theeNB, as shown in FIG. 9 which schematically illustrates the initialsetup of the reporting in this embodiment.

In a ninth embodiment, another reporting procedure is provided. In thisembodiment, the reporting is triggered by eNB (i.e. active reporting)and performed in a Trace Procedure of S1-MME (S1-AP in TS 36.413)interface. In particular, a new IE is added to a CELL TRAFFIC TRACEtriggered by the eNB to report the band usage information to the MME.Table 8 illustrates the CELL TRAFFIC TRACE added with a new IE (BandUsage Report, which is underlined) for all E-RABs and/or a certainE-RAB. In Table 8, the “IE type and reference” of “Band Usage Report” isdefined as “ratio”, and the “Semantics description” is “Unlicensed bandto licensed band”. In other words, in this example, the band usageinformation indicates the ratio of the band usage of the unlicensed bandto the band usage of the licensed band. However, it is obvious that thisform of the band usage information is only an example, and the bandusage information herein can adopt any other suitable form. FIG. 10schematically illustrates the active reporting by the CELL TRAFFIC TRACEaccording to the embodiment.

TABLE 8 CELL TRAFFIC TRACE IE type and Semantics Assigned IE/Group NamePresence Range reference description Criticality Criticality MessageType M 9.2.1.1 YES ignore MME UE S1AP M 9.2.3.3 YES reject ID eNB UES1AP ID M 9.2.3.4 YES reject E-UTRAN Trace M OCTET STRING The E-UTRANTrace ID IE YES ignore ID (8) is composed of the following: TraceReference defined in TS 32.422 [10] (leftmost 6 octets, with PLMNinformation coded as in 9.2.3.8), and Trace Recording Session Referencedefined in TS 32.422 [10] (last 2 octets). E-UTRAN CGI M 9.2.1.38 YESignore Trace Collection M Transport Layer Defined in TS 32.422 [10] YESignore Entity IP Address Address 9.2.2.1 Privacy Indicator O ENUMERATEDYES ignore (Immediate MDT, Logged MDT, . . .) E-RAB to Be O 1 YES ignoreReport List >E-RAB O 1 . . . <maxnoofE- EACH ignore to Be Report ItemRABs> IEs >>E-RAB ID O 9.2.1.2 — >>Band O Ratio Unlicensed band tolicensed YES ignore Usage Report band Band Usage O Ratio Unlicensed bandto licensed YES ignore Report band

In this above, the reporting from the eNB to the MME is described indetail by embodiments. After the MME receives the band usageinformation, the MME can report the band usage information to the SGW,and the SGW can report the band usage information to the PGW. Thereporting from the MME to the SGW and from the SGW to the PGW can beperformed by GTP (GPRS Tunnelling Protocol)-based interfaces (S11,S5/S8). In the following, the reporting of the band usage informationfrom the MME to the SGW and from the SGW to the PGW will be described byembodiments.

In a tenth embodiment, the band usage information is actively reportedto from the MME to the SGW or from the SGW to the PGW. In particular,the band usage information is reported from the MME to the SGW and fromthe SGW to the PGW by adding a new IE in a BEARER CONTEXT TO BE MODIFIEDWITHIN MODIFY BEARER REQUEST. Table 9 illustrates the BEARER CONTEXT TOBE MODIFIED WITHIN MODIFY BEARER REQUEST added with a new IE (Band usagereport). In Table 9, the “Band Usage Report” is exemplarily defined as“Ratio of unlicensed band to licensed band”, in other words, the bandusage information indicates the ratio of the band usage of theunlicensed band to the band usage of the licensed band. However, it isobvious that this form of the band usage information is only an example,and the band usage information herein can adopt any other suitable form.

TABLE 9 BEARER CONTEXT TO BE MODIFIED WITHIN MODIFY BEARER REQUESTOctets 1 Bearer Context IE Type = 93 (decimal) Octets 2 and 3 Length = nOctets 4 Spare and Instance fields Information elements PCondition/Comment IE Type Ins. EPS Bearer ID M See NOTE2. EBI 0 S1eNodeB F-TEID C This IE shall be sent on the S11 interface if the S1-Uis being F-TEID 0 used: for an eUTRAN initial attach a UE triggeredService Request in all S1-U GTP-U tunnel setup procedure during a TAUprocedure (see 3GPP TS 24.301 [23])/ handover cases. If an MME is awarethat the eNodeB supports both IP address types, the MME shall send bothIP addresses within an F-TEID IE. If only one IP address is included,then the SGW shall assume that the eNodeB does not support the other IPaddress type. S5/8-U SGW F-TEID C This IE shall be sent on the S5/S8interfaces for a Handover or a F-TEID 1 TAU/RAU with a SGW change. S12RNC F-TEID C If available, this IE shall be included if the message issent on the F-TEID 2 S4 interface if S12 interface is being used. If anS4-SGSN is aware that the RNC supports both IP address types, the S4-SGSN shall send both IP addresses within an F-TEID IE. If only one IPaddress is included, then the SGW shall assume that the RNC does notsupport the other IP address type. See NOTE2. S4-U SGSN F-TEID C Ifavailable, this IE shall be included if the message is sent on theF-TEID 3 S4 interface, if S4-U is being used. If an S4-SGSN supportsboth IP address types, the S4-SGSN shall send both IP addresses withinan F-TEID IE. If only one IP address is included, then the SGW shallassume that the S4-SGSN does not support the other IP address type.Band usage report O Ratio of unlicensed band to licensed band Ratio 0NOTE 1: If only EPS Bearer ID IE is included in the Bearer Context to bemodified IE during the TAU/RAU without SGW change procedure, the SGWshall remove the stored SGSN/RNC/eNodeB userplane F-TEID locally. NOTE2:When Direct Tunnel is used in 3G, e.g. during a Service Requestprocedure if the UE requests to establish a partial set of radio accessbearers and if the SGSN accepts it, or during an SRNS relocationprocedure with some bearer contexts being preserved, the SGSN shallprovide EBI(s) without S12 RNC F-TEID(s) for these bearer context(s)without corresponding radio access bearer(s) being established. The SGWshall be able to handle these bearer context(s). However, in earlierreleases this behaviour may not be supported by the SGW and hence forsuch SGW, the SGSN shall provide EBI together with S12 RNC F-TEID foreach of the bearer context(s) in the Bearer Context to be modified IE.

In an eleventh embodiment, the band usage information is passivelyreported from the MME to the SGW or from the SGW to the PGW. Inparticular, the band usage information is reported from the MME to theSGW or from the SGW to the PGW by adding a new IE in a BEARER CONTEXTWITHIN UPDATE BEARER REQUEST for triggering and adding a new IE in aBEARER CONTEXT WITHIN UPDATE BEARER RESPONSE for reporting. Tables 10and 11 respectively illustrate the BEARER CONTEXT WITHIN UPDATE BEARERREQUEST added with a new IE (Band usage Query) and the BEARER CONTEXTWITHIN UPDATE BEARER RESPONSE added with a new IE (Band usage Report).In Table 11, the “Band Usage Report” is exemplarily defined as “Ratio ofunlicensed band to licensed band”, in other words, the band usageinformation indicates the ratio of the band usage of the unlicensed bandto the band usage of the licensed band. However, it is obvious that thisform of the band usage information is only an example, and the bandusage information herein can adopt any other suitable form.

TABLE 10 BEARER CONTEXT WITHIN UPDATE BEARER REQUEST Octet 1 BearerContext IE Type = 93 (decimal) Octets 2 and 3 Length = n Octet 4 Spareand Instance fields Information elements P Condition/Comment IE TypeIns. EPS Bearer ID M EBI 0 TFT C This IE shall be included on the S5/S8,S4/S11 and S2a/S2b Bearer TFT 0 interfaces if message relates to BearerModification and TFT change. Bearer Level QoS C This IE shall beincluded on the S5/S8, S4/S11 and S2a/S2b Bearer QoS 0 interfaces if QoSmodification is requested Bearer Flags O Applicable flags: Bearer Flags0 PPC (Prohibit Payload Compression): this flag may be set on the S5/S8and S4/S11 interfaces. vSRVCC indicator: This IE may be included by thePGW on the S5/S8 interface according to 3GPP TS 23.216 [43]. Whenreceived from S5/S8, SGW shall forward on the S11 interface. ProtocolConfiguration CO PGW shall include Protocol Configuration Options (PCO)IE on PCO 0 Options (PCO) the S5/S8 interface, if available. This bearerlevel IE takes precedence over the PCO IE in the message body if theyboth exist. If SGW receives this IE, SGW shall forward it to SGSN/MME onthe S4/S11 interface. Band Usage Query O ENUMERATED (true) 0

TABLE 11 BEARER CONTEXT WITHIN UPDATE BEARER RESPONSE Octet 1 BearerContext IE Type = 93 (decimal) Octets 2 and 3 Length = n Octet 4 Spareand Instance fields Information elements P Condition/Comment IE TypeIns. EPS Bearer ID M EBI 0 Cause M This IE Indicates if the bearerhandling was successful, and if Cause 0 not, gives information on thereason. S4-U SGSN F-TEID C This IE shall be included on the S4 interfacewhen direct tunnel F-TEID 0 is not established. See NOTE 1. S12 RNCF-TEID C This IE shall be included on the S4 interface when directtunnel F-TEID 1 flag is set to 1. See NOTE 1. Protocol Configuration COAn MME/SGSN shall include the PCO IE if such information PCO 0 Options(PCO) was received from the UE. If the SGW receives this IE, the SGWshall forward it to PGW on the S5/S8 interface. This bearer level IEtakes precedence over the PCO IE in the message body if they both exist.Band Usage Report O Ratio of unlicensed band to licensed band Ratio 0NOTE 1: In some scenarios, the SGSN is unable to provide neither the S12RNC F-TEID nor the S4-U SGSN F-TEID in the Update Bearer Responsemessage, e.g. when Direct Tunnel is used in 3G and the UE is in IDLEmode, for a network requested user location retrieval procedure, theSGSN is unable to provide S12 RNC F-TEID. In those scenarios, the SGSNshall provide EBI(s) without S12 RNC F-TEID(s) and S4-U SGSN F-TEID. TheSGW shall be able to handle these bearer context(s). However, in earlierreleases this behaviour may not be supported by the SGW and hence forsuch an SGW, in order to be backward compatible, the SGSN shall provideEBI(s) together with either the S4-U SGSN F-TEID or the S12 RNC F-TEID.

In the eleventh embodiment, when reporting from the MME to the SGW, theSGW sends a BEARER CONTEXT WITHIN UPDATE BEARER REQUEST to the MME fortriggering, and the MME feedbacks a BEARER CONTEXT WITHIN UPDATE BEARERRESPONSE to the SGW for reporting. When reporting from the SGW to thePGW, the PGW sends a BEARER CONTEXT WITHIN UPDATE BEARER REQUEST to theSGW for triggering, and the SGW feedbacks a BEARER CONTEXT WITHIN UPDATEBEARER RESPONSE to the PGW for reporting.

From the above embodiments, it can be seen that the band usageinformation can be actively or passively reported by the eNB to the CN.Each valid period for the band usage information can be configured asrequired. For example, one valid period for the band usage informationcan be time between last two trigger events if the reporting of the bandusage information is passively triggered by the CN; or time from lastreporting to current reporting if the reporting of the band usageinformation is actively performed by the eNB; or time between two switchevents between the first band and the second band.

After the band usage information arrives at the PGW, PCEF (Policy andCharging Enforcement Function), PCRF (Policy and Charging RulesFunction), OFCS (OFfline Charging System) and OCS (Online ChargingSystem) will handle the charging based on the band usage information.Various charging policies can be adopted to process the charging, forexample, to discount the payment (e.g. lower price on unlicensed band),or refund data volume to users. For example, in case of OFCS (refer to3GPP TS 32.240: Telecommunication management; Charging management;Charging architecture and principles), band usage report (band usageinformation) is indicated from Rf, then OFCS generates the charging ofdata volume of each bearer based on corresponding band usage report. Incase of OCS (TS 32.240), band usage report is indicated from R0 and/orGy. OCS reserves or blocks a certain amount of (monetary ornon-monetary) units as using licensed band on the subscriber's account,and permission to use an amount of resources that matches the unitreservation is returned to the network. After transmission, the actualamount of resource usage (i.e. the used units for licensed band andunlicensed band respectively) is deduced from the band usage report tothe OCS so that eventually over-reserved amounts can be re-credited tothe subscriber account. For example, for a pre-pay user, units in thelicensed band are firstly reserved or blocked, then over-reserved unitsare returned to the user's account based on the band usage information;and for a post-pay user, a bill will be generated based on the bandusage information.

It is noted that the above mentioned protocols whose details are omittedin the above description can refer to related specifications such as TS36.413, TS 32.240, and so on.

Further, as mentioned in the above, the band usage information can alsobe generated at the UE. In this regard, the present disclosure alsoprovides a band usage information generating and reporting method 1100for wireless communication performed by a UE, as shown in FIG. 11. Themethod 1100 comprises: a band usage information generating step 1101 ofgenerating band usage information for charging; and a band usageinformation reporting step 1102 of reporting the band usage informationto a core network (CN) by Non-Access Stratum (NAS), wherein the bandusage information involves band usage of at least a first band and asecond band, and traffic is assigned to respective bands by an eNB towhich the UE is attached. It is noted that the band usage informationgenerating procedures at the eNB described in the above can also beapplied to the band usage information generating step 1101 unless thecontext indicates otherwise.

In addition, an eNB, a CN, a MME and a UE for performing the abovedescribed methods are also proposed in the present disclosure. It isnoted that the above descriptions for the methods can also be applied tothe eNB, CN, MME and UE provided herein.

FIG. 12 is a block diagram illustrating an eNB 1200 for generating andreporting band usage information for wireless communication according toan embodiment of the present disclosure. The eNB 1200 comprises: a bandusage information generating unit 1201 configured to generate band usageinformation for charging; and a band usage information reporting unit1202 configured to report the band usage information to a core network(CN), wherein the band usage information involves band usage of at leasta first band and a second band, and traffic is assigned to respectivebands by the eNB.

The eNB 1200 according to the present disclosure may optionally includea CPU (Central Processing Unit) 1210 for executing related programs toprocess various data and control operations of respective units in theeNB 1200, a ROM (Read Only Memory) 1213 for storing various programsrequired for performing various process and control by the CPU 1210, aRAM (Random Access Memory) 1215 for storing intermediate datatemporarily produced in the procedure of process and control by the CPU1210, and/or a storage unit 1217 for storing various programs, data andso on. The above band usage information generating unit 1201, band usageinformation reporting unit 1202, CPU 1210, ROM 1213, RAM 1215 and/orstorage unit 1217 etc. may be interconnected via data and/or command bus1220 and transfer signals between one another.

Respective units as described above do not limit the scope of thepresent disclosure. According to one implementation of the disclosure,the functions of the above band usage information generating unit 1201and band usage information reporting unit 1202 may be implemented byhardware, and the above CPU 1210, ROM 1213, RAM 1215 and/or storage unit1217 may not be necessary. Alternatively, the functions of the aboveband usage information generating unit 1201 and band usage informationreporting unit 1202 may also be implemented by functional software incombination with the above CPU 1210, ROM 1213, RAM 1215 and/or storageunit 1217 etc.

The present disclosure also provides a mobility management entity (MME)for communicating band usage information for wireless communication,comprising: a band usage information receiving unit that receives bandusage information for charging from an eNB; and a band usage informationreporting unit that reports the band usage information to a PGW via aSGW, wherein the band usage information involves band usage of at leasta first band and a second band, and traffic is assigned to respectivebands by the eNB. An exemplary block diagram of the MME can be similarto FIG. 12 except that the above band usage information generating unitand band usage information reporting unit are replaced by the band usageinformation receiving unit and the band usage information reportingunit. The above description related to FIG. 12 is also applied herein.

The present disclosure also provides a user equipment (UE) forgenerating and reporting band usage information for wirelesscommunication, comprising: a band usage information generating unit thatgenerates band usage information for charging; and a band usageinformation reporting unit that reports the band usage information to acore network (CN) by Non-Access Stratum (NAS), wherein the band usageinformation involves band usage of at least a first band and a secondband, and traffic is assigned to respective bands by an eNB to which theUE is attached. An exemplary block diagram of the UE can be similar toFIG. 12, and the above description related to FIG. 12 is also appliedherein.

In addition, the present disclosure also provides a core network (CN)for processing charging for wireless communication, comprising: a bandusage information obtaining unit configured to obtain band usageinformation for charging from an eNB; and a charging processing unitconfigured to process the charging based on the band usage information,wherein the band usage information involves band usage of at least afirst band and a second band, and traffic is assigned to respectivebands by the eNB. It is noted that the band usage information obtainingunit and the charging processing unit can be any different elements orthe same element(s) in the CN. For example, the band usage informationobtaining unit can be a MME, or the combination of a MME, a SGW and aPGW. The charging processing unit can be a charging system or any otherone or more elements with this function in the CN. In other words, theband usage information obtaining unit and the charging processing unitare not limited by its implementation forms. In particular, the presentdisclosure can provide a CN comprising at least a MME, a SGW and a PGWas illustrated in FIG. 2. The definitions of the MME, the SGW and thePGW can refer to the above descriptions concerning the charging methodperformed by the CN.

The present disclosure can be realized by software, hardware, orsoftware in cooperation with hardware. Each functional block used in thedescription of each embodiment described above can be realized by an LSIas an integrated circuit. They may be individually formed as chips, orone chip may be formed so as to include a part or all of the functionalblocks. The LSI here may be referred to as an IC, a system LSI, a superLSI, or an ultra LSI depending on a difference in the degree ofintegration. However, the technique of implementing an integratedcircuit is not limited to the LSI and may be realized by using adedicated circuit or a general-purpose processor. In addition, a FPGA(Field Programmable Gate Array) that can be programmed after themanufacture of the LSI or a reconfigurable processor in which theconnections and the settings of circuits cells disposed inside the LSIcan be reconfigured may be used. Further, the calculation of eachfunctional block can be performed by using calculating means, forexample, including a DSP or a CPU, and the processing step of eachfunction may be recorded on a recording medium as a program forexecution. Furthermore, when a technology for implementing an integratedcircuit that substitutes the LSI appears in accordance with theadvancement of the semiconductor technology or other derivativetechnologies, it is apparent that the functional block may be integratedby using such technologies.

It is noted that the present disclosure intends to be variously changedor modified by those skilled in the art based on the descriptionpresented in the specification and known technologies without departingfrom the content and the scope of the present disclosure, and suchchanges and applications fall within the scope that claimed to beprotected. Furthermore, in a range not departing from the content of thepresent disclosure, the constituent elements of the above-describedembodiments may be arbitrarily combined.

1. An integrated circuit configured to control a process of a basestation, wherein the process includes: generating band usage informationfor charging, wherein the band usage information relates to band usageof at least a first band and a second band, the first band is a licensedband and the second band is an unlicensed band both supported by thebase station, traffic is assigned to respective bands by the basestation, and the band usage information of the second band is providedon a per bearer basis and per time interval, wherein the time intervalis configured as time between two events passively triggered by amanagement entity or configured as time from last reporting to currentreporting actively performed by the base station; and transmitting aband usage information report of the band usage information to a corenetwork entity, wherein, at a Packet Data Convergence Protocol (PDCP)layer, band usage of all or successfully received PDCP service dataunits (SDUs) is counted for the first band and the second band,respectively, to generate the band usage information, and wherein, intransparent mode radio link control (RLC): at a medium access control(MAC) layer, band usage state of each RLC protocol data unit (PDU) isreported to the PDCP layer; and at the PDCP layer, the band usage of allor successfully received PDCP SDUs is counted based on the band usagestate of corresponding RLC PDUs to generate the band usage information.2. The integrated circuit according to claim 1, wherein the band usageinformation of the second band is generated using Internet Protocol (IP)layer packets and without using Packet Data Convergence Protocol (PDCP)headers.
 3. The integrated circuit according to claim 1, wherein thetransmitting includes transmitting the band usage information report toa packet data network gateway (PGW) via a mobility management entity(MME) and a serving gateway (SGW).
 4. The integrated circuit accordingto claim 3, wherein the transmitting includes transmitting the bandusage information report to the MME by S1-AP interface, wherein aninitial setup is performed by adding a new information element (IE) inan INITIAL CONTEXT SETUP REQUEST from the MME.
 5. The integrated circuitaccording to claim 3, wherein the transmitting includes transmitting theband usage information report to the MME by S1-AP interface, wherein aninitial setup is performed by adding a new information element (IE) inan E-RAB SETUP REQUEST from the MME.
 6. The integrated circuit accordingto claim 1, comprising: circuitry configured to execute the process; andan output node, which is coupled to the circuitry and which, inoperation, outputs data.
 7. An integrated circuit configured to controla base station, comprising: circuitry, which, in operation, generatesband usage information for charging, wherein the band usage informationrelates to band usage of at least a first band and a second band, thefirst band is a licensed band and the second band is an unlicensed bandboth supported by the base station, traffic is assigned to respectivebands by the base station, and the band usage information of the secondband is provided on a per bearer basis and per time interval, whereinthe time interval is configured as time between two events passivelytriggered by a management entity or configured as time from lastreporting to current reporting actively performed by the base station;and transmission circuitry, which, in operation, controls transmitting aband usage information report of the band usage information to a corenetwork entity, wherein, at a Packet Data Convergence Protocol (PDCP)layer, band usage of all or successfully received PDCP service dataunits (SDUs) is counted for the first band and the second band,respectively, to generate the band usage information, and wherein, intransparent mode radio link control (RLC): at a medium access control(MAC) layer, band usage state of each RLC protocol data unit (PDU) isreported to the PDCP layer; and at the PDCP layer, the band usage of allor successfully received PDCP SDUs is counted based on the band usagestate of corresponding RLC PDUs to generate the band usage information.8. The integrated circuit according to claim 7, wherein the band usageinformation of the second band is generated using Internet Protocol (IP)layer packets and without using Packet Data Convergence Protocol (PDCP)headers.
 9. The integrated circuit according to claim 7, wherein thetransmitting includes transmitting the band usage information report toa packet data network gateway (PGW) via a mobility management entity(MME) and a serving gateway (SGW).
 10. The integrated circuit accordingto claim 9, wherein the transmitting includes transmitting the bandusage information report to the MME by S1-AP interface, wherein aninitial setup is performed by adding a new information element (IE) inan INITIAL CONTEXT SETUP REQUEST from the MME.
 11. The integratedcircuit according to claim 9, wherein the transmitting includestransmitting the band usage information report to the MME by S1-APinterface, wherein an initial setup is performed by adding a newinformation element (IE) in an E-RAB SETUP REQUEST from the MME.